Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1036

reference
448-tree-1
name
1036
tree-preservation-order

undefined

448-tpo-1
uprn
address-text
point
POINT (-1.011042 50.890968)
geometry
MULTIPOLYGON (((-1.010971 50.890961,-1.010974 50.890975,-1.010984 50.890987,-1.010999 50.890997,-1.011019 50.891004,-1.011041 50.891006,-1.011063 50.891004,-1.011083 50.890998,-1.011099 50.890988,-1.011109 50.890976,-1.011113 50.890962,-1.011110 50.890948,-1.011100 50.890935,-1.011084 50.890925,-1.011065 50.890919,-1.011043 50.890916,-1.011021 50.890918,-1.011001 50.890925,-1.010985 50.890934,-1.010974 50.890947,-1.010971 50.890961)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL